Release 16.10.2025 (Evening) - Facebook Pixel Tracking Fixes - #608
Merged
Conversation
- Changed fbq.q initialization from [] to fbq.q || [] to preserve queue - Added check to only initialize fbq if it doesn't exist - Fixes issue where init and PageView calls were lost before script loaded - Now all pages globally track PageView on load via Layout component
- Added [Tracking] prefix to all tracking logs for easy filtering - Log initialization of each service (GA, LinkedIn, Facebook) - Log all tracking calls (PageView, events, form interactions, registrations) - Log when services are skipped due to missing config - Makes debugging tracking issues much easier in dev and production
Co-authored-by: Cameron Taylor <50385537+ct3685@users.noreply.github.com>
…ing (#607) ## Summary - Fixed Facebook Pixel queue property bug preventing events from firing - Restored global PageView tracking on all docs pages - Fixed form interaction tracking to use custom events instead of Lead - Added comprehensive debugging logs for tracking verification ## Changes - **Fixed critical bug**: Changed `fbq.q` to `fbq.queue` to match official Facebook implementation - **Added callMethod check**: Proper handling of queued events before/after script load - **Global PageView tracking**: PageView now fires on all docs pages via Layout component - **Form tracking fix**: Changed form start from Lead event to FormStarted custom event - **Enhanced debugging**: Added detailed console logs with `[Tracking]` prefix for all initialization and events ## Test plan - [x] Verify PageView fires on all docs pages (not just webinar pages) - [x] Verify Facebook Pixel Helper detects the pixel - [x] Verify network requests to facebook.com/tr appear - [x] Verify FormStarted custom event fires (not Lead) - [x] Verify CompleteRegistration fires on form submission - [x] Check console logs show proper initialization and queue state ## Technical details Facebook Pixel tracking was broken because we used `fbq.q` instead of the official `fbq.queue` property. When fbevents.js loaded, it couldn't find queued events. Now matches official Facebook stub implementation exactly.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
maxtechera
temporarily deployed
to
staging - aai-unified2-flowise-moonstruck
October 16, 2025 18:18 — with 
Render
Inactive
Render
Inactive
This was referenced Oct 22, 2025
maxtechera
added a commit
that referenced
this pull request
Oct 23, 2025
## 📦 Release Summary This release includes updates from staging to production, bringing multiple improvements, fixes, and new features. ## 🎯 Key Changes ### Recent Updates - **HOTFIX**: Remove metadata from Stripe events - **fix**: Handle Stripe 35-day limitation for historical billing data (#624) - **chore**: Updates to fix publish automation (#623) - **feat**: Added automation for publishing aai-embed-react (#616) - **feat**: Comprehensive export/import functionality enhancement (AAI-501) (#469) ### Previous Releases Included - Billing Metadata Filtering - 22.10.2025 (#622) - Chat Drawer Pagination - 22.10.2025 (#621) - Billing Tag Self-Healing and Optimized Trace Fetching (#617) - Facebook Pixel Tracking Fixes (#608) - JLINC audit log, env overrides, and partnership page updates (#597) - Analytics tracing, billing accuracy, and admin navigation fixes (#591) ## 📊 Impact Summary - **Files changed**: 2956 files - **Additions**: 312,083 lines - **Deletions**: 25,803 lines ## ✅ Pre-Release Checklist - [ ] All tests passing on staging environment - [ ] No critical errors in staging logs - [ ] Database migrations reviewed and tested - [ ] Environment variables documented - [ ] Monitoring alerts configured - [ ] Rollback plan documented ## 🚀 Deployment Notes This is a standard release from staging to production. Please ensure all pre-release checks are completed before approving. --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: DiegoC <diecoscai@gmail.com> Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Cameron Taylor <50385537+ct3685@users.noreply.github.com> Co-authored-by: Jaime Morales <jaime.raul.morales@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release Summary
Hot-fix release addressing critical Facebook Pixel tracking issues and documentation improvements.
🐛 Bug Fixes
Facebook Pixel Tracking Implementation (#607)
fbq.qtofbq.queueto match official implementationTechnical Details:
callMethodcheck andfbq.pushassignment per Facebook specDocumentation Improvements (#589)
pnpm startcommand from local development instructions📊 Impact
🧪 Testing
📝 Commits
🚀 Deployment Notes
No special deployment steps required. Changes are client-side tracking code that will take effect immediately upon deployment.
Release Date: October 16, 2025 (Evening)
Severity: High Priority (Tracking Fix)
Type: Hot-fix Release